_EEEE_LLLL_OOOO_OOOO_PPPP Too many symbolic links were encountered in
translating the pathname in _n_a_m_e.
_EEEE_IIII_OOOO An I/O error occurred while making the directory
entry or allocating the inode.
_EEEE_RRRR_OOOO_FFFF_SSSS The inode would reside on a read-only file system.
_EEEE_IIII_SSSS_DDDD_IIII_RRRR A null pathname was specified.
SSSSEEEEEEEE AAAALLLLSSSSOOOO
_uuuu_nnnn_llll_iiii_nnnn_kkkk(2)
NNNNOOOOTTTTEEEESSSS
Binding a name in the UNIX domain creates a socket in the file system
that must be deleted by the caller when it is no longer needed (using
_uuuu_nnnn_llll_iiii_nnnn_kkkk(2)).
The rules used in name binding vary between communication domains.
The type of address structure passed to _bbbb_iiii_nnnn_dddd() depends on the address
family. UNIX domain sockets (address family _AAAA_FFFF______UUUU_NNNN_IIII_XXXX) require a _ssss_tttt_rrrr_uuuu_cccc_tttt
_ssss_oooo_cccc_kkkk_eeee_tttt_aaaa_dddd_dddd_rrrr______uuuu_nnnn as defined in _ssss_yyyy_ssss_////_uuuu_nnnn_...._hhhh; Internet domain sockets (address
family _AAAA_FFFF______IIII_NNNN_EEEE_TTTT) require a _ssss_tttt_rrrr_uuuu_cccc_tttt _ssss_oooo_cccc_kkkk_aaaa_dddd_dddd_rrrr______iiii_nnnn as defined in _nnnn_eeee_tttt_iiii_nnnn_eeee_tttt_////_iiii_nnnn_...._hhhh.
Other address families may require other structures. Use the structure
appropriate to the address family; cast the structure address to a
generic _cccc_aaaa_dddd_dddd_rrrr______tttt in the call to _bbbb_iiii_nnnn_dddd() and pass the size of the structure